Timer use in extensible firmware interface compliant systems

ABSTRACT

Methods, systems, apparatuses and program products are disclosed for providing timer use and timer based execution parallelism during the DXE phase of computer start-up. 
     Provision is made for loading a microkernel (or other kernel program) which presents itself as though it were a DXE Driver and changes a single threaded environment into a multithreaded environment.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional application for a patent No. 61/268,562 entitled. INNOVATIONS IN SECURECORE TIANO 2.0 filed Jun. 13, 2009 inventor Stephen E. Jones and which is incorporated in its entirety by this reference. This application is related to United States patent application entitled “EXECUTION PARALLELISM IN EXTENSIBLE FIRMWARE INTERFACE COMPLIANT SYSTEMS” by Stephen E. Jones who is the same inventor as for this application.

FIELD OF THE INVENTION

The present invention generally relates to personal computers and devices sharing similar architectures and, more particularly relates to a system and corresponding method for timer use and timer based execution parallelism in a DXE (Driver Execution Environment) phase of a PC (personal computer) startup process. Similar processes within comparable computing apparatuses or within a single computer operational session or context also fall within the general scope of the invention.

BACKGROUND OF THE INVENTION

Modernly, the use of PCs (personal computers), including so-called laptop and notebook computers, is increasingly common and the computers themselves are ever more powerful and complex. A persistent problem is the unduly long elapsed time between the moment of power-on and the time when the PC has become ready for user stimulus and/or to initiate useful work.

Intel® Corporation first defined EFI (Extensible Firmware Interface) as the programming interface exposed by firmware to O/S (operating system); former comparable firmwares were not sufficiently portable nor scalable to Intel's CPU (Central Processor Unit) IA64 architecture. A first implementation of the EFI interface became known as Tiano, which Intel® Corporation offered under license via a web site. The UEFI Forum (Unified EFI Forum), a trade group, secured architectural control over EFI (and derivatives thereof) under a new name—UEFI, with a right to support and extend. The UEFI Forum documents and specifies the UEFI interface.

The PIWG (Platform Initialization Working Group) of the UEFI Forum provides a common internal framework for Silicon and platform drivers, so that a common understanding of the roles and methods used by Silicon and platform drivers is developed by implementers of UEFI firmware stacks together with the providers of the Silicon and platform drivers.

The UEFI and related standards provide richness, but fail to sufficiently address significant specific areas of concern including:

-   -   Quality of board bring-up user experience     -   Quality of BIOS customization experience     -   Duration of system bootloading and platform initialization time     -   Level of reliability     -   Level of compatibility with Intel's Foundation Core (also known         as Foundation for short and a part of Tiano)     -   Scope for platform innovation by BIOS (basic input-output         system) vendors and partners and customers thereof.

These attributes are described in the current version of SCT (SecureCore Tiano™) System Overview published by Phoenix® Technologies Ltd. Adequately addressing all of these areas of concern requires innovation above and beyond what is described in UEFI and PIWG standards. However, innovation needs to be at least backwards compatible with those same standards so as not to lose benefits of compliance therewith.

The EFI/UEFI environments provide for DXE (Driver Execution Environment) firmware running in a limited execution environment with a fixed control policy. A sole means of communication between drivers is the so-called Protocol, a means for drivers to publish pointers to internal routines and data so that other drivers may call and exploit them. Drivers, also known as device drivers are well-known in the computing arts. Although running in protected mode, with 32-bit or 64-bit addressability, the DXE environment implements drivers as connected islands of functional capabilities.

This environment relies on dependency expressions of protocols exposed by DXE drivers, and upon a schedule of DXE drivers to be loaded in a desirable order. Once loaded, DXE drivers are run once, publishing protocols as necessary, so that they might be called again only when their services are requested through published protocols. Limited services are provided by the Foundation for a DXE Driver to gain control on a timer tick, as well as being notified when an O/S loads or has finished loading. Functionality is thereby limited, perhaps unduly limited in view of the specific areas of concern previously mentioned. UEFI lacks a structural framework for execution that is sufficiently flexibly adaptable to problems presented in practical embodiments.

However, UEFI Specification(s) offer considerable richness by making it possible to combine drivers together into stacks in many different ways to form new compound capabilities. In this way UEFI compliant products may contemplate taking on a large problem space for the future.

While UEFI's protocols are well-defined, the execution vehicles providing support for drivers that implement these protocols in the native EFI environment is relatively primitive. There exists a need to provide a more pragmatic extension of the Foundation that provides modern programming paradigms while remaining compatible with existing EFI/UEFI practice and especially with unmodified drivers for a smooth transition to exploitation of the improved capabilities.

A significant advantage of embodiments of the invention over previously developed solutions is that it becomes possible to make improvements by implementing execution parallelism and/or associated time-sharing within a DXE phase of computer loading and initialization.

SUMMARY OF THE INVENTION

The present invention provides a method for operating a computer and also an apparatus that embodies the method. In addition program products and other means for exploiting the invention are presented.

According to an aspect of the present invention an embodiment of the invention may provide a method for providing timer use and timer based execution parallelism during the DXE and even the BDS (Boot Device Selection) phases of computer start-up. This may include loading and initializing a computer comprising executing an EFI-style Foundation, loading a Kernel that has a thread creation and supervision capability, creating an ISR (interrupt service routine) to hook a timer interrupt and reentering the EFI core program as a first thread supervised by the kernel. Kernels are well-known in the computing arts and refer to a central part of a software, firmware or microcode implementation and which have far reaching control at run time. Microkernels are also well-known; they have components that run at mutually differing privilege levels, interrupt levels or some such scheme.

Further provided for may be the loading of DXE Driver programs that create threads and block themselves without blocking an underlying DXE Foundation program.

BRIEF DESCRIPTION OF THE DRAWINGS

The aforementioned and related advantages and features of the present invention will become better understood and appreciated upon review of the following detailed description of the invention, taken in conjunction with the following drawings, which are incorporated in and constitute a part of the specification, illustrate an embodiment of the invention and wherein like numerals represent like elements, and in which:

FIG. 1 is a schematic block diagram of an electronic device configured to implement the present invention;

FIG. 2 shows an event sequence diagram according to an embodiment of the present invention.

FIG. 3 shows relationships between major hardware, firmware and software components according to an embodiment of the invention.

FIG. 4A show a sequence of acts in which part of an embodiment of the invention is depicted.

FIG. 4B is a continuation of the acts described in connection with FIG. 4A.

FIG. 4C is a further sequence of acts for an ISR (interrupt service routine) according to an embodiment of the invention.

FIG. 4D is a flow sequence related to another (alternative or additional) embodiment of the invention.

FIG. 4E is a continuation of the acts described in connection with FIG. 4D.

FIG. 5 shows how an exemplary embodiment of the invention may be encoded onto a computer medium or media; and

FIG. 6 shows how an exemplary embodiment of the invention may be encoded, transmitted, received and decoded using electro-magnetic waves.

DETAILED DESCRIPTION OF THE INVENTION

The numerous components shown in the drawings are presented to provide a person of ordinary skill in the art a thorough, enabling disclosure of the present invention. The description of well known components is not included within this description so as not to obscure the disclosure or take away or otherwise reduce the novelty of the present invention and the main benefits provided thereby.

Embodiments of the disclosure presented herein provide methods, systems, apparatus, and computer-readable media for providing and utilizing a means for time saving parallel execution capability in a context of PC startup and initialization. In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements throughout the several figures, aspects of an exemplary operating environment and the implementations provided herein will be described.

An exemplary embodiment of the present invention will now be described with reference to the figures. FIG. 1 is a schematic block diagram of an electronic device configured to implement the operational functionality according to the present invention.

FIG. 1 shows a computer 10 that is operative to provide an EFI/UEFI firmware environment to provide a DXE phase and that facilitates timer use and timer based execution parallelism during the DXE phase and even beyond such as into the BDS phase. The computer 10 typically includes a baseboard, or motherboard form of printed circuit board to which a multitude of components or devices are connected by way of a system bus or other electrical communication path. In one illustrative embodiment, a CPU (central processing unit) 12 operates in conjunction with a chipset 50. The CPU 12 is a standard central processor that performs arithmetic and logical operations necessary for the operation of the computer.

Chipset 50 may include a Northbridge 14 and a Southbridge 32. The Northbridge 14 may be attached to CPU 12 by a FSB (Front Side Bus) 13 and typically provides an interface between the CPU 12 and the remainder of the computer 10. The Northbridge 14 may also provide an interface to a RAM (random access memory) 16 the main memory for the computer 10 and, possibly, to other devices such as an on-board graphics adapter (not shown in FIG. 1).

The Northbridge 14 is connected to a Southbridge 32 by a DMI (direct media interface) 18. The Southbridge 32 may be responsible for controlling many of the input/output functions of the computer 10 such as USB (universal serial bus), sound adapters, Ethernet controllers and one or more GPIO (general purpose input/output) port (None shown in FIG. 1). In one embodiment, a bus comprises a PCI (peripheral component interconnect) bus circuit 22 to which a disk storage subsystem 66 (often abbreviated to “disk”) or other storage devices for storing an operating system and application programs may be attached.

The Southbridge 32 may also provide SMM (system management mode) circuits and power management circuitry. A peripheral interface 30 may also be provided by the Southbridge 32 for connecting a Superl/O (Super input-output) device 60. Southbridge 32 may also incorporate a timer circuit for generating timer circuit interrupts typically at periodic intervals.

As known to those skilled in the art, an O/S (operating system) such as may be stored on disk 66 comprises a set of programs that control operations of a computer and allocation of resources. An application program is software that runs on top of the O/S software and uses computer resources made available through the O/S to perform application specific tasks desired by the user.

Disk 66 may also provide non-volatile storage for the computer 10. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the computer 10. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, serial EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices well-known in the art, or any other medium which can be used to store the desired information and which can be accessed by the computer.

The peripheral interface 30 may also connect a computer storage media such as a ROM (Read-only memory, not shown) or, more typically, a flash memory such as a NVRAM (non-volatile random access semiconductor memory) 33 for storing UEFI platform firmware 34 that includes program code containing the basic routines that help to start up the computer 10 and to transfer information between elements within the computer 10. The UEFI firmware 34 is compatible with the UEFI Specification.

It should be appreciated that the computer 10 may comprise other types of computing devices, including hand-held computers, embedded computer systems, personal digital assistants, and other types of computing devices known to those skilled in the art. It is also contemplated that the computer 10 may not include all of the components shown in FIG. 1, may include other components that are not explicitly shown in FIG. 1, or may utilize an architecture different from that shown in FIG. 1.

FIG. 2 shows an event sequence diagram to illustrate an embodiment of operations performed by a computer system initializing in a EFI/UEFI conforming manner, that is following the EFI/UEFI Framework and according to an embodiment of the invention. Details regarding the operation and architecture of EFI/UEFI can be found in the appropriate previously developed and published documentation.

The process is divided into several phases, including a SEC (Security) phase 202, a PEI (Pre-EFI Initialization) phase 204, a DXE (Driver Execution Environment) phase 206, a BDS (Boot Device Selection) phase 208, a TSL (Transient System Load) phase 210, an O/S RT (Run-Time) phase 212, and an AL (After-Life) phase 214. The phases progressively provide a run-time environment for the PC applications.

The SEC phase 202 supports security checks from power-on initiation and authenticates the Foundation as a requirement prior to safely executing it.

The PEI phase 204 provides a standardized method of loading and invoking specific initial configuration routines for the processor, chipset, and motherboard. This phase initializes sufficient system to provide a stable base for continuing. Initialization of core components including CPU, chipset and main motherboard occurs. The PEI phase locates and configures memory and hands it off to the DXE phase immediately following.

The DXE phase 206 is where much of the implementation of embodiments of the invention is to be found. This is the phase during which most of the system initialization is performed. The DXE phase 206 uses a DXE Core, a DXE Dispatcher (also known as the Driver Dispatcher) and a plurality of DXE Driver programs. The DXE Core provides Boot Services, Runtime Services, and DXE Services. The Driver Dispatcher discovers, loads and initiates DXE Drivers according to a pre-defined sequence The DXE drivers initialize components and provide services (including software abstractions of some devices).

The BDS phase 208 further prepares the computer system to load an O/S. This may include such well known programs as GRUB (Grand Unified Bootloader)

The TSL phase 210 facilitiates services to be available to an O/S loader. The RT (Run Time) phase 212, is largely software, rather than firmware controlled and includes application programs. EFI Runtime services reemerge in the AL (After Life) phase 214 in connection with winding-up operations.

FIG. 3 shows relationships between major hardware, firmware and software components according to an embodiment of the invention. Referring to FIG. 3, platform firmware 310 comprises one or more modules 320 compliant with the EFI Specification (Extensible Firmware Interface from Intel Corporation) or UEFI (Unified EFI) Specification (from the UEFI Forum—a trade organization). EFI and UEFI specifications describe an interface between O/S (Operating System) 340 and the platform firmware 310. EFI and UEFI specifications also describe the interface platform firmware 310 implements in support of bootloading interface used by O/S 340.

Platform firmwares are implemented in various ways within compliance with EFI and UEFI specifications and also include a BIOS 330 that provides a level of support for access to Hardware Platform 350. Hardware Platform 350 can itself come in multiple guises including hardware per se, as well as supporting microcoded engines and the like.

Embodiments of the invention provide a new Kernel architecture at the bottom of an execution stack that can expose new execution and communication vehicles. Also a PE32+ loader that supports dynamic linking, and augments the Foundation Core's loader services in a way that does not modify the Foundation itself is present. PE32+ program formats and loaders for such are well-known in the art. System policies may be implemented, including configuration, security, and boot policies. Execution context vehicles allow DXE drivers to load in a legacy (previously developed EFI DXE) context, in an SMM context, and in a virtual machine, or even in other contexts still to be anticipated.

One such other context may be the STM (SMM Transfer Monitor) feature which essentially provides for virtualization (or similar) of code which might otherwise be expected to operate in SMM (or at least is designed or compatible thereto). Alternatively (arguably equivalently) one may regard STM as a form of hypervisor that virtualizes the CPU's SMM itself. STM can be considered as a not yet mature technology and implementation details of it may evolve.

A provided DXE phase innovation of particular interest is the provision of timer-based execution parallelism through incorporation of a microkernel (though a monolithic Kernel could also be used within the general scope of the invention). Microkernels provide functionality through their KPI (kernel program interface), in the form of functions callable by DXE drivers and UEFI applications. A microkernel may support elemental objects providing execution vehicles, including threads, timers, interrupts, DPCs (deferred procedure calls), power-fail notifications, and power resume notifications.

In embodiments of the invention threads are a central feature of execution parallelism. Kernel threads are in general well-known in the art of O/Ses but have not heretofore been applied in the present non-obvious implementations. Threads are used in the inventive UEFI DXE and/or BDS phase environment(s) to provide parallelism, boosting performance such as by simplifying expression of solutions from state machines to threaded designs.

In previously developed EFI/UEFI environments, DXE drivers receive control once they are loaded, and do not subsequently execute until they are called via an exposed protocol. This requires them to perform initialization of their managed controller, bus, or device either at initialization time or at the time a connect request is made through a protocol. Because device initialization often involves polling for devices and waiting for them to become ready (e.g. hard drive spin-up, or keyboard startup) these, or other, delays are serialized resulting in undue delays and hence overly large boot times.

In embodiments of the invention DXE Drivers may allocate threads by calling a Kernel function, for example by passing as a parameter a pointer to the driver function to be executed in parallel by the new thread. Execution may thus continue in parallel on a thread context even while the driver initialization routine returns control to the DXE Foundation program.

Inside thread functions, other Kernel services may be called, as can EFI services, including EFI Boot Services and so-called EFI Run Time Services.

To achieve even greater parallelism, a driver may create a thread for each logical or physical device it manages. Additional threads may be allocated to perform periodic cleanup tasks, or health measurement, thus offering new benefits. Threads may be configured to run in a separate VM (Virtual Machine) or even in a separate core of a multi-core processor according to expressed DXE Driver requirements.

Threads may be provided inside all or many execution contexts, in the native DXE environment, an SMM environment, and/or virtualized environments, thus allowing comparable programming paradigms to be adapted across implemented contextual modes.

Kernel may also offer a lightweight mechanism for scheduling execution of a function at a future point in time with dynamic granularity, supported across all execution contexts and based on provision of timer service(s).

In previously developed solutions, DXE drivers typically use an Event Boot Service to schedule the execution of a function on a timer tick. However, this method does not scale well such as across SMM and/or virtualized environments. By implementing more native, more configurable, object across all contexts, and exposing respective kernel services to DXE drivers and to Executive programs, the Kernel is able to provide uniform dispatching of deadline-based execution in the system.

Moreover, the Kernel may be configured to use the Foundation's Event services to provide the source of control for dispatching its timers and threads, or the Kernel may be configured to implement a virtualized Event service using the Kernel's more lightweight services, by hooking the DXE phase Boot Services table. The latter may allow a Foundation's Event service to be supported across all execution contexts.

Interrupt objects may also be provided by Kernel thus offering an execution vehicle to respond to a hardware event, for example an interrupt generated by an APIC (Advanced Programmable Interrupt Controller), a SMI (System Management Interrupt) generated by the system's own chipset when a non-interrupting hardware event occurs, or through virtualization traps of I/O (input/output) or memory space.

Without Kernel capabilities, interrupts other than the Event timer tick might not be supportable in DXE Drivers; however, interrupts are needed in order to receive notice of events happening in physical worlds, including during POST (Power-On Self Test), during O/S load, after O/S load, or even when O/S fails.

Thus, with interrupts supported by the Kernel, DXE drivers have not need to make resource-consuming (and time-wasting) polls for devices to complete their I/O This allows those CPU cycles to be used more productively than heretofore thus resulting in accelerated boot times. Moreover, kernel may schedule multiple threads by sharing time between them according to any of various scheduling algorithms well-known in the art in which threads are scheduled from time to time. Scheduled from time to time means, in this context, that every thread is continually accorded an opportunity to run but not necessarily at any predetermined moment in time nor after any predetermined interval.

Referring to FIG. 4A, a sequence of acts in which part of an embodiment of the invention is depicted as starting at ref. 4100, in a context of an EFI or UEFI compliant PC startup sequence having completed the first phase of startup from power-on (the SEC or Security phase).

At Ref. 4110, the pre-EFI phase is performed. This phase tends to be quite hardware specific and related to the type of controller and memory chips available. Both cache and main memory must be configured in and main memory is not available for general purpose use at the start of the pre-EFI phase, but becomes available at some point. Thus rather specialized techniques have evolved, for example chips which will eventually be configured as cache memory may initially be used as main memory while the main memory chips themselves are probed and configured in.

At Ref. 4120, control passes to the DXE (Driver execution environment) Foundation code which is highly standardized and operates as described earlier in the present document. By design the DXE Foundation code is intended to single thread through the loadable DXE Drivers. In the present embodiment this single thread through DXE Foundation and DXE Driver is retained but with some of the DXE Drivers acquiring additional threads. But in other embodiments the DXE Foundation code may be executed responsive to one or more interrupts as described below (See for example FIG. 4C).

At Ref. 4130, the EFI Driver dispatcher (which is part of the EFI or UEFI Foundation program) discovers the Kernel program and at Ref. 4140 loads it into main memory and passes control to it. By design, the dispatcher searches for and discovers DXE drivers so the Kernel program is presented as appearing (to the dispatcher) to be a DXE Driver. Loosely speaking one might say the Kernel is disguised to look like a DXE Driver program and it is loaded before any DXE Drivers proper. Typically, though not essentially, Kernel will be loaded from (having been previously stored in) stored in NVRAM rather than hard disk since it is rather fixed for the platform and typically has an intimate relationship with (other) parts of BIOS. In an alternative embodiment within the general scope of the invention, it is possible for Kernel to be executed directly out of a ROM, however there are well-known disadvantages to such an approach even though it is substantially compatible and/or equivalent.

At Ref. 4150, Kernel creates an ISR (Interrupt Service Routine) and hooks a related interrupt; typically though not essentially this ISR is attached to a hardware periodic timer interrupt. The usual technique, well known in the art, for doing this is to create an ISR (Interrupt Service Routine) and patch into (also known as hook) the appropriate interrupt vector. EFUUEFI Foundation code expressly permits DXE Drivers to hook the timer in this way, and indeed it is to be expected that in previously developed solutions, one or more DXE Drivers would do exactly that. A purpose of the ISR is that it allows Kernel to recapture execution control at a later date without being expressly called by EFI Foundation or by any other non-preemptive means such as a non-priority service request from a DXE driver.

At Ref. 4160 Kernel may create and export (make available) at least one thread-creation service. This service will be used later by actual DXE Drivers as described below. Methods for exporting services including inter-process calls are well known in the art.

At Ref. 4190, control is returned (by exiting) to the Driver Dispatcher that called Kernel, at this time the environment is still executing as a single thread. However Kernel has exported a service for creating threads, that service is typically invoked at a later moment by DXE Drivers. With execution now out of Kernel and back in Foundation, the end of FIG. 4A is reached and control may pass to the entry point into FIG. 4B in some embodiments of the invention.

Referring to FIG. 4B, which may be regarded as a continuation of the acts described in connection with FIG. 4A, the process continues at Ref. 4200 in the DXE Foundation code. At Ref. 4210, the first actual DXE Driver (i.e. excluding the Kernel program) is located by Dispatcher and loaded into memory and entered.

At Ref. 4230 the DXE Driver program invokes the Kernel's service to create a new thread having located the service using the information that arose out of the Kernel's exporting the service. Export of service is described above in connection with at Ref. 4160 in the discussion of FIG. 4A.

At Ref. 4240 the Kernel creates the new thread and initializes it. Kernel supervises time-sharing between the threads whenever there is more than one activated thread. In an embodiment Kernel provides for thread execution preemptively such as by switching at time of servicing a hooked interrupt which is typically a timer interrupt. When there is more than one thread created then kernel may schedule the threads based on a switching context which may be due to a thread blocking itself (such as waiting for a message or an event) or alternatively preemptively such when servicing the ISR (or any of the various ISRs in some embodiments of the invention). A single DXE Driver may create one thread, multiple threads or no thread at all. Techniques for threading, blocking etc. are well-known techniques implemented in many Kernel programs.

At Ref. 4250, a first thread belonging to the first DXE driver is in existence even though (in a typical embodiment) not executing at that moment. At Ref. 4290 the control returns to the DXE Driver still on the original (unthreaded) flow. It will be apparent to persons of ordinary skill in the art that execution may continue, as described below, so that other DXE Drivers may be loaded and may create further threads thus providing more parallelism in execution. In a large practical embodiment there may be dozens, if not hundreds, of DXE Drivers not all of which require their own threads.

Referring now to FIG. 4C, at 4300 an ISR in the Kernel program is entered from a hardware interrupt. There may be interrupt processing associated with the hardware or the interrupt itself (not shown in FIG. 4C and not critical to the invention). The issue of when (and how) to enable interrupts is also important but not an essential feature of the invention, it may be done at this point in the flow or it may be done later.

Entering the ISR enables the Kernel to acquire control. At 4310, the Kernel performs its scheduling activity; scheduling can be complex but is well known in the art.

At 4320 at determination is made as to whether a thread created by a DXE Driver is ready to run. If no DXE thread is ready to run (they are all blocked) then at 4390 there is a return (or a reentry) to the DXE Foundation code. Alternatively, even if a thread is ready to run it may be found (at ref. 4330) that the DXE Foundation code should be run anyway in preference to running a DXE Driver thread at this time. This may be, for example, because the DXE Foundation appears to have been starved of cycles and it is simply time to give it a share of the available CPU cycle resource (by transferring control to 4390).

Otherwise control may pass to 4340 and a DXE driver is run on its thread, or one of its plurality of threads. The DXE Driver might be resumed at the point in the flow at which it was interrupted, or if it previously blocked itself (such as waiting for an event) then it may be resumed responsively to an associated unblocking by Kernel.

At 4350, flow may return from the DXE Driver, such as if the Driver blocks itself, as part of a termination procedure or if it simply voluntarily yields control. If such cases flow may return to ref. 4310 where scheduling is performed anew.

Referring to FIG. 4D, a flow related to another (alternative or additional) embodiment of the invention is described hereinafter.

Starting at ref. 4100, in a context of an EFI or UEFI compliant PC startup sequence having completed the first phase of startup from power-on (the SEC or Security phase). Also, a the pre-EFI phase is performed similar to the acts of FIG. 4A

At Ref 4420, control passes to the DXE (Driver execution environment) Foundation code. At Ref. 4430, the Dispatcher (EFI Driver Dispatcher) discovers the Kernel program and at Ref. 4440 loads it into main memory and passes control to it. The dispatcher searches for and discovers DXE drivers so the Kernel program is presented as appearing (to the dispatcher) to be a DXE Driver as before. Discovering DXE programs and loading them is a primary function of dispatcher.

At Ref. 4450, Kernel creates an ISR (Interrupt Service Routine) and hooks a related interrupt; typically the periodic timer interrupt. At Ref. 4460 The kernel performs its functions as previously described. This includes exporting thread creation protocol services and scheduling. Initially, of course, at first execution, there will be no threads to schedule. Then, at Ref. 4470, having completed work presently required, Kernel blocks itself. However, the context is saved so that return may be made later to Foundation from a timer flow (see below).

Referring now to FIG. 4E, at 4500 the ISR created by and in the Kernel program is entered from a hardware interrupt. At ref. 4510 there may be interrupt processing associated with the hardware or the interrupt itself. Interrupts will be enabled and at ref. 4520 a decision is made as to whether the DXE Foundation program is already running. On a first time through this code DXE Foundation will not be running so the entry point at which it originally called kernel can be used to return to, or reenter Foundation, as shown at ref. 4350. Other techniques will be apparent to persons of ordinary skill in the art to provide equivalent and similar means to run Foundation on a flow of code responsive to the timer interrupt. Kernel may or may not be unblocked at this point according to precise details of implementation.

Similarly and conversely, the context which was present before the interrupt is retained and can (usually will) be used later by kernel to restore flow.

At Ref. 4540, on subsequent executions of the ISR, the kernel will simply be unblocked so it can poll for work and at ref. 4590 control is returned to the prior context. Thus, several methods of implementation have been described to support the invention as claimed and equivalent approaches may be possible within the general scope of the claimed invention.

As is well known in the art, threads may terminate themselves when their work is done, often first creating events to notify their completion to other cooperating entities. However such behaviors, though commonplace, are not to be seen as a critical feature of the invention.

With regards to FIG. 5, computer instructions to be incorporated into an electronic device 10 may be distributed as manufactured firmware and/or software computer products 510 using a variety of possible media 530 having the instructions recorded thereon such as by using a storage recorder 520. Often in products as complex as those that deploy the invention, more than one medium may be used, both in distribution and in manufacturing relevant product. Only one medium is shown in FIG. 5 for clarity but more than one medium may be used and a single computer product may be divided among a plurality of media.

FIG. 6 shows how an exemplary embodiment of the invention may be encoded, transmitted, received and decoded using electro-magnetic waves.

With regard to FIG. 6, additionally, and especially since the rise in Internet usage, computer products 610 may be distributed by encoding them into signals modulated as a wave. The resulting waveforms may then be transmitted by a transmitter 640, propagated as tangible modulated electro-magnetic carrier waves 650 and received by a receiver 660. Upon reception they may be demodulated and the signal decoded into a further version or copy of the computer product 611 in a memory or other storage device that is part of a second electronic device 11 and typically similar in nature to electronic device 10.

Other topologies and/or devices could also be used to construct alternative embodiments of the invention. The embodiments described above are exemplary rather than limiting and the bounds of the invention should be determined from the claims. Although preferred embodiments of the present invention have been described in detail hereinabove, it should be clearly understood that many variations and/or modifications of the basic inventive concepts herein taught which may appear to those skilled in the present art will still fall within the spirit and scope of the present invention, as defined in the appended claims. 

1. A method for loading and initializing a computer comprising: executing an EFI (extensible firmware interface) core program to load a kernel program into a memory; first executing the kernel program to create an ISR (interrupt service routine); further executing the kernel program to export a service for creating threads; and returning from the kernel program to the EFI core program.
 2. The method of claim 1 further comprising: executing the EFI core program to load a first driver program; executing the first driver program to invoke the service for creating threads; executing the service for creating threads to create and initialize a first thread supervised by the kernel program; and further executing the first driver program to return control to the EFI core program.
 3. The method of claim 2 further comprising: executing the ISR to activate or reactivate the first thread.
 4. The method of claim 3 further comprising: executing the EFI core program to load a second driver program; executing the second driver program to invoke the service for creating threads; executing the service for creating threads to create and initialize a second thread supervised by the kernel program; and continually executing the ISR to schedule a thread selected from the first thread and the second thread wherein both the first thread and the second thread are scheduled from time to time.
 5. The method of claim 4 wherein: the ISR hooks a timer circuit interrupt.
 6. The method of claim 4 wherein: the second thread is initiated to run in a VM (virtual machine) distinct from the VM in which the first thread runs.
 7. The method of claim 4 wherein: the second thread is initiated to run on a micro-processor core distinct from the multi-processor core in which the first thread runs.
 8. The method of claim 2 wherein: the first driver program is a DXE (Driver Execution Environment) program.
 9. The method of claim 8 wherein: the kernel program exports a service to provide a timer and the first driver program invokes the service to provide a timer.
 10. The method of claim 9 wherein: the service to provide a timer provides dynamic granularity.
 11. The method of claim 2 wherein: the first thread is initiated to run in SMM (system management mode).
 12. The method of claim 2 wherein: the kernel program exports a service to provide a timer and the first driver program invokes the service to provide a timer.
 13. The method of claim 2 wherein: the first thread is initiated to run in a virtualized SMM (System Management Mode).
 14. The method of claim 2 wherein: the kernel program exports a service to provide an interrupt service response to a SMI (system management interrupt).
 15. The method of claim 1 wherein: the ISR hooks a timer circuit interrupt.
 16. A method for loading and initializing a computer comprising: executing an EFI (extensible firmware interface) core program to load a kernel program into a memory; first executing the kernel program to create an ISE (interrupt service routine); responsive to an interrupt, executing the ISR to reenter the EFI core program; further executing the kernel program to export a service for creating threads; and a DXE program invoking the service for creating threads.
 17. The method of claim 16 further comprising: executing the EFI core program to load a first driver program; executing the first driver program to invoke the service for creating threads; and executing the service for creating threads to create and initialize a first thread supervised by the kernel program.
 18. The method of claim 17 further comprising: executing the EFI core program to load a second driver program; executing the second driver program to invoke the service for creating threads; and executing the service for creating threads to create and initialize a second thread supervised by the kernel program; and continually executing the kernel program to schedule a thread selected from the first thread and the second thread wherein both the first thread and the second thread are scheduled from time to time.
 19. The method of claim 18 wherein: the kernel program schedules the first thread and the second thread responsive to an interrupt.
 20. The method of claim 19 wherein: the interrupt is a timer circuit interrupt.
 21. The method of claim 18 wherein: the first and second driver programs are DXE (Driver Execution Environment) programs.
 22. The method of claim 18 wherein: the second thread is initiated to run in a VM (virtual machine) distinct from the VM in which the first threads runs.
 23. The method of claim 18 wherein: the second thread is initiated to run on a multi-processor core distinct from the multi-processor core in which the first thread runs.
 24. The method of claim 17 wherein: the first driver program is a DXE (Driver Execution Environment) program.
 25. The method of claim 17 wherein: the first thread is initiated to run in SMM (system management mode).
 26. The method of claim 17 wherein: the kernel exports a service to provide a timer and the first driver program invokes the service to provide a timer.
 27. The method of claim 17 wherein: the kernel exports a service to provide a timer and the first driver program invokes the service to provide a timer.
 28. The method of claim 27 wherein: the service to provide a timer provides dynamic granularity.
 29. The method of claim 17 wherein: the first thread is initiated to run in a virtualized SMM (System Management Mode).
 30. The method of claim 17 wherein: the kernel exports a service to provide an interrupt service response to a SMI (system management interrupt).
 31. The method of claim 16 wherein: the ISR hooks a timer circuit interrupt.
 32. A computer program product comprising: at least one non-transitory computer-readable medium having instructions persistently stored therein, the instructions when executed by at least one processor causes the at least one processor to perform: executing an EFI (extensible firmware interface) core program to load a kernel program into a memory; first executing the kernel program to create an ISR (interrupt service routine); further executing the kernel program to export a service for creating threads; and returning from the kernel program to the EFI core program.
 33. A computer program product comprising: at least one non-transitory computer-readable medium having instructions persistently stored therein, the instructions when executed by at least one processor causes the at least one processor to perform: executing an EFI (extensible firmware interface) core program to load a kernel program into a memory; first executing the kernel program to create an ISE (interrupt service routine); responsive to an interrupt, executing the ISR to reenter the EFI core program; further executing the kernel program to export a service for creating threads; and a DXE program invoking the service for creating threads.
 34. An electronic device comprising: a controller; and a first system memory having instructions encoded therein, the instructions when executed by the controller cause said controller to operate by steps to perform: executing an EFI (extensible firmware interface) core program to load a kernel program into a memory; first executing the kernel program to create an ISR (interrupt service routine); further executing the kernel program to export a service for creating threads; and returning from the kernel program to the EFI core program.
 35. An electronic device comprising: a controller; and a first system memory having instructions encoded therein, the instructions when executed by the controller cause said controller to operate by steps to perform: executing an EFI (extensible firmware interface) core program to load a kernel program into a memory; first executing the kernel program to create an ISE (interrupt service routine); responsive to an interrupt, executing the ISR to reenter the EFI core program; further executing the kernel program to export a service for creating threads; and a DXE program invoking the service for creating threads. 